Template Configuration
The substitution codes that output specific fields of data are enclosed in single chevron brackets< > e.g., <bn> will substitute the Booking Name.
A higher level of codes - enclosed in double chevron brackets << >> are used to define distinct sections within the template e.g., optional services or to indicate specific sections of the message e.g., pax names.
In addition to section codes and substitution codes, there are conditional codes that assist with the formatting and output of the message e.g., removing blank rows or containing email send commands.
The message template Body (Lines) Section can have different Line formats to suit different types of messages and different types of services. In addition to information, such as supplier name and address, services like transfers need to show a pick-up and drop-off date, time, and place. Sightseeing services need a service date (and possibly time); accommodation services need an in and out date, room types, and meals included. Products have a Message Format Type code attached to them that tells the system which format type to use for each product when the message is generated. In the event that a product does not have a Service Format Code attached, a "Default" format type must be included in each message template to allow some detail to be output for those products.
The example message in Message Configuration was created using this template.
Although the example itinerary template includes the Default, AC (Accommodation), EF (Entry Fees), ME (Meals), TF (Transfers), and PK (Package Tours), only the Default, AC service formats were used in the booking. Selected template sections are detailed below.
The code <rms:row> does not have any output and it is used to remove an entire row from a table if no data is returned by the subsequent substitution code.
Message Header Section
Message Body Section - <<Default>> Service Format
Message Body Section - <<AC>> Accommodation Service Format
Message Tail Section